Subject: APPN TRS Protocols Reference Page Numbering Off

From: [email-masked]
Date: Mon, 18 Apr 94 17:41:43 EDT

Willi,

You're right about a lot of stuff being added to the APPN TRS protocols
chapter over the last year.  All modifications made to TRS since
the APPN Reference book was last published have been announced and presented
at our last two AIW conferences.  There are six of them in total.

I have been systematically converting these documents to PostScript and FTPing
them up to the IBMstandards repository over the last three weeks.  So far,
three of the modifications are on IBMstandards already, the fourth document
will be put up within the week.  One of the documents not currently up there,
and was a heavy hit to TRS, is Topology Awareness of CP-CP sessions.  This
modification affected four major APPN components.  We are still working out
a couple of editorial corrections to this modification, but should have the
final version up on the repository by next week.  The sixth modification
still has unresolved issues associated with it.  They should be resolved soon,
and when that happens this document will also be place on the repository.
Following is a complete list of the modifications that have formally been
introduced to the TRS chapter since our last APPN Reference book has been
published:

    Description of Modification                       # of Pages    On IBM-
                                                      Modified      Standards?
    ==========================================================================

1.  Interpreting Mode or COS names in Route Requests   11           Yes
2.  Don't Increment NN's own RSN in Topology Exchange  3            Yes
3.  Strip NetID from TG partner name when building     3            Yes
    routes
4.  Topology Awareness of CP-CP Sessions               25           No (A)
5.  Building Routes through Connection Networks        5            No (B)
6.  Using FRSN values during Topology Exchange with    8            No
    nonSafe Storing NNs

(A)  Still making editorial changes
(B)  Issues still needing to be resolved

Regards,

Tim Hefel  APPN Architecture